home *** CD-ROM | disk | FTP | other *** search
- .TOPIC:
- VirtualNET
-
- VBBS 6.12 Documentation -- 9-A-1
-
-
- ╔════════════════════════════════════════════════════════════════╗
- ║ CHAPTER NINE ANNEX A VIRTUALNET ║
- ╚════════════════════════════════════════════════════════════════╝
-
-
- WHAT IS VIRTUALNET?
- ═══════════════════
-
- VirtualNET is a wide area network of on-line bulletin board
- systems and mail servers. The link acomplishing this is the Virtual
- BBS software authored by Roland De Graaf. The purpose of VirtualNET
- is to provide a variety of discussion areas and sub-boards for bull-
- etin board users. It also provides technical support for VBBS soft-
- ware, and interaction between VirtualNET SysOps. This fast growing
- network is open to all newcomers who wish to join. VirtualNET is
- public networked message areas, private message areas, electronic
- mail, and more!
-
- VirtualNET has the current distinction of being the fastest
- growing amateur network in the nation. With effort on the part of all
- pioneering VirtualNET SysOps, VirtualNET will continue to grow at an
- exponential rate.
-
- Founded in 1990 by Roland De Graaf and John Bok, VirtualNET is
- managed by its Network Coordinator, Regional Coordinators, and Area
- Coordinators.
-
-
- NETWORKED MESSAGE AREAS
- ═══════════════════════
-
- VirtualNET sports 3 different kinds of Public/Private Networked
- Message areas: AutoRequest, AutoSubscription, and Secured. AutoRequest
- and AutoSubscription sub-boards are considered public sub-boards,
- while Secured subs are more private in nature. All Message Areas are
- identified by a "Sub Number."
-
- Setting up new subs on your VBBS can BE accomplished either
- thru "VCONFIG", or thru Neil J Marshall's "VAREA" program.
-
-
- AUTOREQUEST & AUTOSUBSCRIPTION
- ══════════════════════════════
-
- Subscribing to autorequest type subs is easy. Just use VCONFIG
- or VAREA to set them up. You will be able to send and receive posts
- almost immediately. "Hosting" of an autorequest subs is difficult,
- since it is not possible to prevent systems from accessing an auto-
- request type sub-board.
-
-
- SECURED SUBS
- ════════════
-
- Subscribing to secured subs takes a little more work. These
- subs have a clearly defined Host, who can add or remove systems at
-
- VBBS 6.12 Documentation -- 9-A-2
-
-
- his/her own discretion. Setting up a secured sub can be done auto-
- matically, thru the VAREA program, or manually thru VCONFIG. A Host
- of a secured sub must create a "distribution list" of the systems to
- receive a particular sub. Subscribers must be sure to identify the
- host. (For more information on setting up Secured and AutoSecured,
- please see XXXXX.XXX.)
-
-
- E-MAIL
- ══════
-
- Private E-Mail routing is a function of the network. Each user
- on your system has a unique VirtualNET address and if given appro-
- priate security may send and receive mail across the network. Note
- that your BBS must be properly listed in the networked BBSLISTs in
- order for E-Mail routing to work properly. There is nothing further
- you need to set-up. Note: VBBS allows for Carbon-Copy and MultiMail
- List facilities. You must not allow your users to abuse such func-
- tions on the network.
-
- TAGLINES
- ════════
-
- Taglines are a great way to personalize posts, and appear as a
- stamp on the bottom of each posted message. System taglines are made
- optional for each message base. Taglines are limited by the software
- and by VirtualNET policy to 3 lines of "ascii" or "heart code" color
- with a maximum size of 300 bytes (characters).
-
- Taglines are a great thing and can be quite informative. SOME
- network sub hosts however, do not allow the use of taglines in their
- subs. If you carry "gated" subs or are part of another network, it is
- recommended that you familiarize yourself with policy related to
- tagline usage.
-
-
- JOINING VIRTUALNET
- ══════════════════
-
- Included with the VBBS program, is a list of VirtualNET BBSs
- which is current at the time of the release (BBSLIST files). If you
- would like to have your BBS join VirtualNET or have further questions
- regarding VirtualNET, please contact the Area Coordinator (AC) for
- your area as listed in the BBSLIST files. If your area does not yet
- have an AC, please contact one of the VirtualNET Regional Coordinators
- (RC) as listed. All RCs can be reached through VirtualNET addresses.
-
- -->SPECIAL NOTE: VBBS/NET version 6.12 installation is REQUIRED before
- joining VirtualNET.
-
- .TOPIC:
- VBBS Officials
-
- VBBS 6.12 Documentation -- 9-A-3
-
-
- VIRTUALNET ADMINISTRATIVE DIRECTORY
- ═══════════════════════════════════
-
- NETWORK COORDINATOR (NC): John Bok 1@6160 VirtualNET
- ASST. NETWORK COORDINATOR (ANC): Gene Wells 1@1604017 VirtualNET
-
- This information prepared on 12-15-1993 @ 11am
-
- REGIONAL COODINATORS
-
- Region 1 (RC1): Mike McKenzie 1@1618002 VirtualNET
- Region 2 (RC2): Bill Snell 1@1610000 VirtualNET
- Region 3 (RC3): Kevin Rouse 1@6190 VirtualNET
- Region 4 (RC4): Dennis Younker 1@1619001 VirtualNET
- Region 5 (RC5): Neil J. Marshall 1@440 VirtualNET
- Region 6 (RC6): Roland Emery 1@1604000 VirtualNET
- Region 7 (RC7): Patrick Murray 1@1919999 VirtualNET
- Region 8 (RC8): John Bok 1@6160 VirtualNET
- Region 9 (RC9): John Hellman 1@1206000 VirtualNET
-
- SubsList: Neil J. Marshall 1@440 VirtualNET
-
- -
-
- REGIONS LISTING
- ═══════════════
-
- REGION 1 (Midwest US) Coordinator: Mike McKenzie 1@1618002 VirtualNET
-
- Minnesota, Iowa, Missouri, Wisconsin, Illinois, Indiana,
- Ohio, Michigan, North Dakota, South Dakota, Nebraska
-
- 218 612 507 712 515 319 816 417 314 715 906 414 608 815 708 309
- 217 618 312 812 317 219 419 216 513 614 616 517 313 605 701 308 402
-
-
- REGION 2 (East US) Coordinator: Bill Snell 1@1610000 VirtualNET
-
- Virginia, W. Virginia, Maryland, Washington DC, Delaware, Maine,
- New Jersey, New York, Pennsylvania, Conneticut, Rhode Island, Ver-
- mont, New Hampshire
-
- 207 802 603 413 508 617 401 203 516 212 718 201 908 609 302 301 703
- 804 304 412 814 215 717 914 607 716 315 518 410
-
-
- REGION 3 (South US) Coordinator: Kevin rouse 1@6190 VirtualNET
-
- Texas, Arkansas, Louisiana, Mississippi, Oklahoma, Kansas
-
- 501 318 504 601 210 806 915 817 214 409 713 512 918 405 316 913 903
-
- VBBS 6.12 Documentation -- 9-A-4
-
- REGION 4 (West US) Coordinator: Dennis Younker 1@1619001 VirtualNET
-
- Washington, Oregon, California, Montana, Idaho, Arizona, Nevada,
- New Mexico, Utah, Wyoming, Colorado, Alaska, Hawaii
-
- 307 801 303 719 702 602 505 406 208 714 310 808 209 805
- 619 916 707 415 818 213 510 808 206 509 503 809 907
-
- REGION 5 (Europe) Coordinator: Neil J. Marshall 1@440 VirtualNET
-
- All European Country Codes
-
- REGION 6 (Canada West) Coordinator: Roland Emery 1@1604000 VirtualNET
-
- All Western Canadian Area Codes
-
- REGION 7 (SouthEast) Coordinator: Patrick Murray 1@1919999 VirtualNET
-
- Kentucky, Florida, Georgia, North Carolina, South Carolina,
- Tennessee, Alabama
-
- 502 606 305 407 813 904 404 912 704 919 803 615 901 205
-
- REGION 8 (Pacific Rim) Coorindator: John Bok 1@6160 VirtualNET
-
- Pacific Rim Area Codes
-
- REGION 9 (Canada East) Coordinator: John Hellman 1@1206000 VirtualNET
-
- All Eastern Candadian Area Code
-
- APPLICATION FOR VIRTUALNET
- ══════════════════════════
-
- To become a node on VirtualNET please fill out the following
- form and return it to the Area Coordination for your area. If you
- do not know who this is then send it to the Region Coordinator.
-
- Your assigned node number will be sent to you and passed on
- through Network E-Mail to the Regional Coordinator for inclusion in
- the international BBSLIST AFTER the applicant has been connected to
- a VirtualNET local server (with 'sysop only' network access) for a
- period of not less than ONE WEEK. Should the AC have reason to feel
- that the applicant requires more time to become acclamated to the
- network or is otherwise not yet prepared, they may extend this
- period but, in NO case should the total period exceed THREE weeks.
-
- In all cases, pending VirtualNET nodes should state that they
- have read and understood the VirtualNET policies contained in the
- Network documentation and to as well understand and agree to the spe-
- cific policies (if any) of his or her Server.
-
- VBBS 6.12 Documentation -- 9-A-5
-
-
- The return of this form to the AC or RC for your region is
- accepeted as proof that you have READ, UNDERSTAND and AGREE to the
- rules of the VirtualNet.
-
- 1. Date of Application:
- 2. Sysop's real name:
- 3. Sysop's handle (if any):
- 4. Address:
- 5. City: 6. State: 7. Zip:
- 8. SysOp Date of birth:
- 9. Voice Phone No.:
- 10. Other Network affiliation (if any):
-
- Node number assignment will be made by the AC or RC. Please
- enter the server you have set up. If you do not have a server the
- AC or RC will arrange one for you.
-
- Replace the X's below with the correct data for your system.
- ══════════════════════════════════════════════════════════════════════
- Node BBS phone System Name Modem Server
- No. Number Type *
- ----- ------------ -------------------- ------ ----
- @XXXXXXXXX XXX-XXX-XXXX XXXXXXXX XXXXXX XXXXXXX XXXX XXXX
-
- 11. Registration No.____________________
- ═══════════════════════════════════════════════════════════════════════
-
- * Modem type e.g 1200, 2400, V32, HST, HST/DS, Not brand name unless
- its a Compucom.
-
- This form is to be returned intact with no changes other than
- the addition of the data. Please do not change the layout of the form
- in any way as it is set up to be read by macros to extract the data
- to the bbslist and a database.
-
- This is the standard form for a new VirtualNET node assignment.
- It gives the AC for your area the needed info to pass on to the Net-
- work RC. It also provides phone numbers to the network administration
- should there ever be a need to contact you. Once you have completed
- this form, please return it to your Area Coordinator or to a VirtualNET
- Regional Coordinator should your area not yet have an AC.
-
- Node assignments are usually effected within a weeks time.
- Generally, you can expect to become official within a few weeks of
- your application. Updates to the BBSLIST.NET are sent out generally
- twice each week by the Regional Coordinators reflecting changes and
- additions made.
-
- VBBS 6.12 Documentation -- 9-A-6
-
-
- THE ROLE OF THE AC
- ══════════════════
-
- (ACs) - At the backbone of VirtualNET are the Area Coordinators.
- They are the ambassadors between their area and VirtualNET. Normally,
- one AC is assigned to each telephone area code. This position is purely
- voluntary. Area Coordinators are assigned by that region's RC.
-
-
- Requirements of the VirtualNET AC-
-
- 1) Be operating an accessable VBBS 24 hours per day.
-
- 2) Be able and willing to provide time and effort toward support and
- the growth of the network.
-
-
- Duties of the VirtualNET ACs-
-
- 1) Promote and support VirtualNET within your area as you are able.
- Encourage and help others to be a part of, and contributors to
- VirtualNET.
-
- 2) Provide a positive image of VirtualNET within the online community.
-
- 3) Resolve conflicts that arise when able within the area and promote
- harmonious participation within the network.
-
- 4) Active participation in the VirtualNET AC sub.
-
- There is NO basis for an arbitrary delay in providing a VBBS
- SysOp with access to the VirtualNET support subs.
-
- It is also recommended that new systems set their networked
- message bases to 255 security level access (SYSOP) until such time
- that their node becomes official in the BBSLIST.
-
- AC's are encouraged to provide at least one Area secured type
- sub for use in discussing local issues and what not, making that sub
- available to all VirtualNET SysOps within his or her area.
-
-
- ESTABLISHING CONNECTS (SERVERS AND CLIENTS)
- ═══════════════════════════════════════════
-
- A new VirtualNET node is asked to make an initial connect with
- that area's AC, or other appointed system for at least one week and
- for as long as three weeks prior to the AC handing a node assignment
- in for addition to the international BBSLIST. The purpose of this is
- to ensure that the new node is fully familiar with the network and
- is setup properly before officially joining the network. This is
- particularly important in cases where that new node will be making
- an official connect directly with a national server.
-
- VBBS 6.12 Documentation -- 9-A-7
-
-
- -->SPECIAL NOTE: Once your Network account has been established, it
- is incumbant upon you as a Client to NET in to your
- Server in a timely manner. Due to matters regarding
- storage of Network Packets, Clients who do not NET
- in to their server for 14 days run the risk of hav-
- ing their pending packet deleted by the Server SysOp,
- unless notification is made. If you are having pro-
- blems, or for whatever reason are not able to receive
- your packet from your Server on a timely basis, be
- sure to contact your Server right away.
-
- Also, if you are going to be leaving the network,
- please notify your Server as well as your Area Coor-
- dinator.
-
-
- THE SUBS LIST
- ═════════════
-
- The VirtualNET Subs List is updated weekly by the Subslist
- Coordinator. The current Subslist appears in your NET directory, in a
- file called SUBSLIST.NET. Note: VAREA makes use of the SUBSLIST.NET
- file to present you with an easy interface for adding and removing
- subs.
-
-
- DECORUM
- ═══════
-
- VirtualNET was founded on the principle of common courtesy. In
- a sense, that is the only VirtualNET "rule". The network is a place
- where information, ideas, and opinions all come together from dif-
- ferent corners in a virtual cornucopia that celebrates the varied
- differences of backgrounds and experiences of those who are a part
- of the network.
-
- First and Foremost, it is a SysOp's unique responsibilty to
- limit Network access on his or her system to responsible users.
- SysOps are expected to handle any problem user which is accessing
- the network from his or her board. In the event that a problem is
- persistant, a warning will be issued to that system. If the problem
- continues, the Network Coordinator will have no choice other than to
- suspend the network connect to the originating node.
-
- To help you "fit in", here are some "do's and don'ts" for the
- net. Some of these are just common sense, but a few have been learned
- from "The BBS School of Experience".
-
- VBBS 6.12 Documentation -- 9-A-8
-
-
- 1. Always remember that you are a guest in many homes, when you post
- on the net. Please keep the language clean. If you read a post
- containing questionable language, please don't quote the ques-
- tionable portion in your public reply. This only gives the post
- greater exposure, and irritates the SysOp's that have to delete your
- post. It is more appropriate to E-MAIL the offending poster, or the
- SysOp of the originating system, rather than start a "flame war"
- with a public reply. There are secured subs that allow the use of
- any style language. Please confine your questionable language to
- these subs.
-
- 2. Sometimes it is better to ignore a post that stirs your ire. If
- you must reply, it is better to make it via E-Mail, rather than a
- public post.
-
- 3. NEVER make something received in E-Mail public, unless you have the
- sender's permission. Making E-Mail public is annoying behaviour and
- may be grounds for removal from the network.
-
- 4. Always try to be helpful toward the newer members. Remember, you
- were new at one time. VirtualNet has grown on it's reputation of
- providing outstanding help for VBBS/VirtualNet problems.
-
- 5. Always try to be factual when you post. This will gain respect for
- you, and build your reputation as one "whose post has merit."
-
- 6. Never "talk down" to anyone. Calling someone an idiot will not win
- friends, nor gain the respect of your fellow net members. If you
- wish to be respected, and maintain a good standing in the network,
- you must respect others.
-
- 7. Remember that it is hard to write something, and have it inter-
- preted in the "tone of voice" that you wrote it. Something meant
- as satire, can come across with a completely different meaning.
- Try to indicate your meaning by symbols, such as :), <grin>, ;),
- <satire>, etc.
-
- 8. VirtualNet has a reputation of being "free and open". As such, the
- threads on some of the subs tend to wander off topic. Please make
- an effort to remain on topic. The net members (and sub hosts) will
- be grateful.
-
- 9. Everyone has "a bad day". Someone will sometimes post something
- that he/she would like to recall. Give the poster the benefit of
- the doubt. Often, an apology will follow a day or so later. In-
- stantly "flaming" the poster will bring ego into play, making a
- retraction impossible.
-
- 10. Realize that a message does not appear on all systems on the same
- day. A message that you reply to, and think settled, may continue
- to receive replies for several days.
-
- VBBS 6.12 Documentation -- 9-A-9
-
-
- 11. Remember that everyone is entitled to their opinion. If you do not
- agree, a cool, reasonable, post stating the reasons for your dis-
- agreement, is much better than lowering yourself to name calling.
- Realize that some people will argue, just for the sake of argument.
- If you find yourself involved with one of this type, swallow your
- pride and let the argument die. It takes two to sustain an
- argument.
-
- 12. Do not belittle anyone's computer, software, etc. Remember that
- you choose your equipment because it best suited your needs. The
- other person may not have the same needs as yourself.
-
- 13. All ADULT material must be propagated via secured sub type,
- and access is the sole responsibility of the sub-host.
-
- 14. The views expressed on VirtualNET are not neccessarily those
- of the VirtualNET staff.
-
- 15. The Network Coordinator may remove any system from the network,
- without prior notification, for any reason.
-
- 16. Any gateways into or out of VirtualNET must be pre-approved by
- SubsList Coordinator.
-
- 17. Use of high-ASCii in To: & From: headers, and in BBSLISTs
- is prohibited. Use of high-ASCii may be totally prohibited
- on certain networks and network gateways.
-
- 18. Taglines must be limited to a maximum of 300 bytes in size,
- and 3 lines in length.
-
-
-
- SUPPORT
- ═══════
-
- Sometimes things don't work quite as they should when first
- establishing a connect with a server. If you have read and followed
- the documentation, and find that you are for whatever reason recieving
- errors, contact your Server! Let him or her know that a problem
- exists and if possible what it is.
-
- VBBS and VirtualNET share the same cooperative support
- structure. Servers, AC's and CORE support boards are there to help you
- should you experience problems. The posts that you send regarding
- problems should always include your Network address (node #), as well
- as your name, software version, WHICH network you're having problems
- with, and whether you are running the program Standalone or as a
- door. It is important as well that you are as specific as possible
- regarding the nature of the problem as well as where it occurs. In-
- variably, almost all errors are the result of something not being
- quite right in the installation.
-
- VBBS 6.12 Documentation -- 9-A-10
-
-
- The Support structure available to you is geared for maximum
- efficiency in resolving problems. No matter who you contact, your mail
- has a good chance of being forwarded within the support structure to
- another SysOp for resolution. This way, not only is the volume of
- support spread more evenly, but as well should result in a more prompt
- and accurate reply to the SysOp requiring support.
-
- As you have access to the VirtualNET Support Subs however,
- please make use of the public support by posting there whenever
- possible as it will provide the greatest benefit to the Net as a whole.
- There is a team of support SysOps affectionately known as the Virtual
- Ski Patrol. These volunteers are there to help resolve problems and
- questions which are posted and generally make sure that all posted
- problems and questions are resolved or answered.
-
- VBBS 6.12 Documentation -- 9-A-1-1
-
-
- ╔════════════════════════════════════════════════════════════════╗
- ║ CHAPTER NINE ANNEX A APPENDIX 1 NETWORK INSTALLATION ║
- ╚════════════════════════════════════════════════════════════════╝
-
-
- GENERAL
- ═══════
-
- In order to use the networking features, you will need to have
- the following programs: (Which VBBS will utilize automatically.)
-
- VXY VBBS Xmodem, Ymodem, Zmodem Driver
- DSZ DSZ External Protocol Driver
- HS-LINK HS-Link Bi-directional Protocol (if desired)
- PKZIP and PKUNZIP PKware ZIP Archive Utilities
-
-
- INSTALLING THE NET
- ══════════════════
-
- The VirtualNET networking software, VNET.EXE is already in-
- cluded with the VBBS program. Once you have recieved your node assign-
- ment and have established yourself as a "client" to a VirtualNET
- "server" you simply need to setup the VirtualNET Network Section in
- VCONFIG. You will need to enter your node number, and the node number
- of your server, and your server's phone number to be able to start
- "netting."
-
-
- EVENTS AND DIALING THRESHOLDS
- ═════════════════════════════
-
- There are two ways to effect automation between Clients and
- Servers. One way is to enable the dialing threshhold in network
- configuration. Once the defined threshold of kb of pending messages
- is met, the software will either call your Server, or poll your
- Clients (if any) depending on the situation. The Local option is active
- 24 hours. Long Distance restricts the time of a particular network
- dialout to between 12am and 8am. Threshold is disabled with a setting
- of 0.
-
- Another way to automate the network is to take advantage of one
- or more of VBBS's 20 definable events. See the VNET command lines
- that follow. These commands can be used from a DOS prompt as well
- as a batchfile and inserted as WFC function keys or as event batch-
- files.
-
-
- PROTOCOL CHOICES
- ════════════════
-
- VirtualNET SysOp's have three choices in transfer protocol
- options. The default choice is VXY Ymodem. Optional protocols are DSZ
- Zmodem, and HSLINK.
-
- VBBS 6.12 Documentation -- 9-A-1-2
-
-
- PHONE CALLING OPTIONS
- ═════════════════════
-
- There are many phone calling options available to Clients mak-
- ing long distance connects. AT&T, MCI and Sprint all have discount
- calling options for off peak calling and frequently called numbers.
- Contact those companies regarding the options available to you.
-
- Another popular calling option for some is a service known as
- PC Pursuit. For more information on PC Pursuit, contact the 800
- information operator (1-800-555-1212) for the 800 PCP information
- desk in your area. The Main VirtualNET server in W. Michigan is NOT
- within an INDIAL PCP area. Other National VirtualNET servers ARE
- however and if you are using PCP, you will need to contact your RC
- regarding the establishment of a PCP connect. Below is an example
- of a PC Pursuit macro for VNET;
-
- {Delete the comments after the double slash (//)).
- Put your local PCP number in the network config in VCONFIG.
- Put this macro in your main VBBS directory and it should work just
- fine.
-
- ----------------Macro starts below this line-------------------------
- SEND @D^M
- SEND D1^M
- RECV @
- SEND D^M
- RECV NOT
- SEND C D/CASJO/24,IDxxxxxxxx,PWxxxx^M // Put your ID, PW and Server's
- // City code here
- RECV D/CASJO/24 CONNECTED // City code goes here also
- SEND I^M // Download the RVPrimer.arc
- SEND ATZ^M // from PC Pursuit or my BBS to
- RECV OK // understand why I did this
- SEND ^E^M // like this instead of using
- RECV HELLO // Hayes command set.
- SEND D7328958^M // Server's Phone Number
- RECV ANSWER TONE // This line was included to
- // delay the Vnet 30 second
- // time out feature.
- ---------------------End of Macro------------------------------------
-
-
- VBBS 6.12 Documentation -- 9-A-2-1
-
- .TOPIC:
- VNet Command Lines
- ╔════════════════════════════════════════════════════════════════╗
- ║ CHAPTER NINE ANNEX A APPENDIX 2 VNET.EXE ║
- ╚════════════════════════════════════════════════════════════════╝
-
- VNET.EXE
- ════════
-
- VNET.EXE is the networking software for the Virtual BBS/NET.
- It should be run out of the same directory as your Virtual BBS. For
- the most part, VBBS.EXE activates VNET.EXE as needed, however there
- are command switches which you may employ during execution from a
- batchfile or Dos prompt.
-
-
- The syntax for VNET.EXE is:
-
- VNET <channel #> <command-switch> NETWORKID=<net id>
-
- Note: If NETWORKID is omitted, Network #1 (VirtualNET) is assumed.
-
- <channel #> specifies which VBBS serial channel to use.
-
- <command-switch> tells VNET what to do, the possibilities are:
-
- /DIAL# - Dial another VirtualNET.
- # is the node address of the system to dial.
-
- /U - Updates all the mail packets.
-
- /A - Analyzes VirtualNET connect and bbslist information sent
- to you from the Network Coordinator.
- Example: VNET /A
-
-
- ╔═╗ Be sure to run VNET Analyze when setting up your Network. The
- ╚═╝ proper syntax is "VNET /A NETWORKID=1". This will compile
- your network information for you and create your "BBSLIST.NET"
- that is required to perform Network connects in VNet.
-
-
- /CHECK - VNET Diagnostics
-
-
- VNET MACROS
- ═══════════
-
- VBBS has the unique ability of VNET.EXE to employ the use
- of macros in establishing a Net connection with another VBBS system.
- If you are running VBBS from a matrix logon or as a door within an-
- other system, you now have the ability to serve as a VirtualNET HOST
- system to other boards from WITHIN the matrix logon or BBS door. If
- you are already the host to a remote VirtualNET system which is run-
- ning in a matrix logon or door, you may now connect to that system for
- polling or whatever.
-
- VBBS 6.12 Documentation -- 9-A-2-2
-
-
- The macro supports 3 commands. All 3 commands are 4 characters
- long, and 1 space is expected between the command and its arguement.
-
- RECV Waits for a string of characters. If they don't show up
- within 30 seconds, the call is aborted.
-
- SEND Sends a string of characters.
-
- WAIT Tells the macro facility what the boards [PAUSE] string is,
- so that it can be handled should it come up when RECV is
- waiting for its string. If it pops up, the macro facility
- automatically sends a 0x0D. The use of this facility is
- optional.
-
- A WWIV example:
-
- WAIT [PAUSE]
- RECV NN:
- SEND Acct name^m
- RECV PW:
- SEND codeword^m
- RECV ###-###-
- SEND 0000^m
- RECV T -
- SEND .
- RECV ?
- SEND 1
-
- The above example logs on to a WWIV board, and runs door # 1.
- Note that you may send and receive control characters by putting a
- "^" in front of them.
-
- When the macro is done executing, VNET.EXE proceeds immediately
- to waiting for the ° which should pop up when VBBS starts running as
- a door.
-
-
- VBBS 6.12 Documentation -- 9-A-3-1
-
-
- ╔════════════════════════════════════════════════════════════════╗
- ║ CHAPTER NINE ANNEX A APPENDIX 3 SUBS HOSTS/MESSAGE SUBS/VAREA║
- ╚════════════════════════════════════════════════════════════════╝
-
-
- PROCEDURES FOR SUB-HOSTS
- ════════════════════════
-
-
- When you have a message base or other networked area which you
- would like to "Host", you will need to first decide what type
- of sub you would like it to be. The (S) secure type subs are
- generally preferable as they are more efficient relative to their
- routing. Autorequest type subs can be desirable for new subs as it
- provides the easist access to them and can give a sub-host a good
- idea how much interest there is in maintaining that networked sub.
- ALL Local type subs, that is those which are national/international
- in nature, as well as ALL "adult" content type subs MUST be (S)
- secure subs according to VirtualNET Policy. Subs which are gated
- into other networks will always follow the rules of that network.
- Sub-hosts of GATED subs shall respect the rules and policies of the
- originating network's sub host (if any) and insure that gateway
- subscribers follow the wishes of that network's sub host. It is
- reccomended that GATED subs use the (S) secure sub types.
- Once you have a networked area that you would like to host, you
- will need to give it a formal name and a description for the
- Subslist Coordinator. If you are hosting a (S) secure sub, you will
- need to post the name and description of the sub, along with the
- sub-host VirtualNET address and the subtype so that it may be
- recorded in the SUBSLIST.NET. If your new network sub is an (A)
- autorequest sub, then you will additionally post a REQUEST to the
- Subslist Coordinator Neil J. Marshall (1@440) for a sub number
- assignment there on the Yellow Pages sub #228. The Yellow pages sub
- should also be used for advertizing your sub (ansi art allowed).
-
-
- SETTING UP SECURED SUBS (V#####.NET and VV#####.NET files)
- ═══════════════════════════════════════════════════════════
-
-
- V#####.NET and VV#####.NET files (##### = sub number) are text
- files that reside in your VBBS network directory.
-
- V#####.NET files are used by sub hosts to set up their list of
- subscribers. It is just a simple text file, with one entry per line.
- The entries are the node numbers of the subscribers.
-
- VV#####.NET files are used by subscribing systems to identify
- the sub host. There is only one entry in a VV#####.NEt file -- the
- node number of the sub host.
-
- VBBS 6.12 Documentation -- 9-A-3-2
-
-
- If you would like to HOST a secured sub:
-
- 1. Determine what sub number you want to use.
- (See below for more info on sub numbering.)
- 2. Create the sub database -- dont forget the sub number!
- 3. Advertise on the Yellow Pages, give the sub number, the sub
- name, a brief description, and the node address of the host
- of the sub.
- 4. As requests for a sub pour in, enter the node numbers, one
- per line, into a V#####.NET file, as ascii text. ##### = sub
- number.
-
- If you would like to SUBSCRIBE to a secured sub:
-
- 1. E-Mail the Host of the sub asking for access.
- (Be sure to specify the sub number.)
- 2. Create a VV#####.NET file containing one line, the node number
- of the sub host. ##### = sub number.
- 3. Create a new database for the sub.
-
- -->SPECIAL NOTE: DON'T forget the sub number!
-
-
- HANDLES/REAL NAMES/ANONYMOUS
- ════════════════════════════
-
- The SysOp has the ability to toggle usage of Handles, Real
- Names or Anonymous posting. All subs will be assumed to be Handles
- unless the sub-host designates otherwise to the Subslist Coordinator.
- Real Names are often required in other networks and if a GATED
- sub requires Real Names then the VirtualNET host is responsible
- for that being made known to the Subslist Coordinator. Anonymous
- posts can be useful for instance in support and recovery type of
- message bases where a sub-host feels that users would be more
- comfortable obscuring their identity altogether.
-
-
- Permanent Messages
- ══════════════════
-
- Permanent messages are a great way for a SysOp to display in a
- message base a synopsis and any rules regarding that message base.
- Sub Hosts may decide from time to time post a message base specific
- permanent message for the subscribing SysOp's to flag for a permanent
- post. When that post reaches the # 1 position, it will not be purged.
- This way, an explanation of the message base can always be found in
- the first post of a message base.
-
- VBBS 6.12 Documentation -- 9-A-3-3
-
-
- VAREA AUTOMATED VNET MESSAGE BASE SUBSCRIPTION UTILITY
- ══════════════════════════════════════════════════════
-
-
- VAREA, programmed by Neil J Marshall, 1@440 VirtualNET, is the
- official message base subscriber utility for VirtualNET. Its a lot
- more fun setting up new message bases with VAREA than with VCONFIG :)
-
- VAREA uses a point-and-shoot type system to select/deselect
- the VirtualNET message bases your system subscribes to.
-
- If you use VAREA, don't forget to add the following to your
- daily event batch file:
-
- VAREA /AUTO NETWORKID=1
-
- Normal startup to use VAREA interactively is:
-
- VAREA NETWORKID=1
-
- Please see the VAREA documentation for more details.
-
-
-